Meta RSP interface platform for eSIM profile distribution

ABSTRACT

A user device may receive a list of remote SIM provisioning (RSP) platforms that are designated by a mobile network operator (MNO) to distribute eSIM profiles of a partner MNO of the MNO, in which the partner MNO provides telecommunication services in a geographical area. The user device may obtain one or more service features of individual RSP platforms in the list of RSP platforms from a meta RSP interface (MRI) platform when the user device is in the geographical area. Subsequently, the user device may determine a number of service parameters that are met by the one or more service features of the individual RSP platforms. In response to identifying a single RSP platform as meeting a highest number of service parameters, the user device may request a download of an eSIM profile from the single RSP platform to access the telecommunication services of the partner MNO.

BACKGROUND

The use of Embedded Universal Integrated Circuit Cards (eUICCs), alsoreferred to as Embedded Subscriber Identity Modules (eSIMs), is becomingincreasingly prevalent in consumer and machine-to-machine (M2M)communication fields. Unlike a traditional UICC or SIM card that existsas a removable smart card that is transferrable between multipledevices, an eUICC is an integrated circuit that is not designed to beuser removable, i.e., it is generally embedded with or soldered to otherelectronic components of a device.

An eUICC may be provisioned with one or more eSIM profiles, in whicheach eSIM profile contains a unique international mobile subscriberidentity (IMSI) number that authenticates a subscriber to a mobilenetwork operator (MNO). Other data that are stored in the eSIM profilemay include carrier network information, security authenticationinformation, a list of accessible network services, and/or so forth,that are specific to the MNO. The MNO may transfer an eSIM profile tothe eUICC of a user device via an over-the-air (OTA) update. Forexample, the user device may be a consumer device. Consumer devices arenetwork-capable devices that are generally marketed to individualconsumers. For example, these devices may include a smartphone, a tabletcomputer, a smartwatch, a gaming console, and/or so forth.

MNOs generally use Remote SIM provisioning (RSP) platforms that areoperated by third parties to provision the eSIM profiles to the eUICCsof user devices. In many instances, an RSP platform may be provided byan eSIM profile vendor that operates a GSM Association (GSMA)-certifieddata center. For example, the eSIM profile vendor may be an eUICCmanufacturer (EUM), and thus is able to generate eSIM profiles forinstallation in the eUICCs.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures, in which the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 illustrates an example architecture for a meta remote SIMprovisioning (RSP) platform to distribute information on various RSPplatforms to a user device such that the user device selects one of theRSP platforms as a provider of an eSIM profile.

FIG. 2 is a block diagram showing various components of one or moreillustrative computing devices that support the meta RSP platform.

FIG. 3 is a block diagram showing various components of an illustrativeuser device that interfaces with the meta RSP platform.

FIG. 4 is a flow diagram of an example process for using the meta RSPplatform to identify a preferred RSP platform for downloading an eSIMprofile of a partner mobile network operator (MNO).

FIGS. 5a and 5b illustrate a flow diagram of an example process forusing the meta RSP platform to identify an RSP platform for downloadingan eSIM profile of a partner MNO based on the service features ofmultiple RSP platforms.

FIG. 6 is a flow diagram of an example process for distributinginformation on the service features of multiple RSP platforms to a localprofile assistant (LPA) application.

DETAILED DESCRIPTION

This disclosure is directed to techniques for providing a meta RSPinterface (MRI) platform that aggregates and stores data on the servicefeatures of multiple RSP platforms. The MRI may be operated by aconsortium of RSP platforms. In some instances, the consortium may be agroup of RSP platforms that are designated by an MNO to provide eSIMprofiles to user devices serviced by the MNO. The service features of anRSP platform may include a geographical area serviced by the RSPplatform, an availability of the RSP platform to distribute eSIMprofiles, a representative response time of the RSP platform to requestsfor eSIM profiles, a reliability rating of the RSP platform indistributing eSIM profiles, available inventory quantities of eSIMprofiles for different user device types that are carried by the RSPplatform, and/or so forth.

Other service features of an RSP platform may include the ability of theRSP platform to provide prioritized provisioning of eSIM profiles to aselective group of user devices that belong to a particularorganization, an ability for the RSP platform to service specializedeSIM profile management operations requested by the MNO or anorganization serviced by the MNO (e.g., eSIM profile duplication,encryption, etc.), and an ability for the RSP platform to supplycustomized eSIM profiles (e.g., eSIM profiles that allow storage ofadditional client data within the profiles).

In various embodiments, a local profile assistant (LPA) application on auser device may have access to a list of preferred RSP platforms for ageographical area, so that the LPA application may download an eSIMprofile of an MNO or a partner MNO from one of the RSP platforms whenthe user device is relocated to the geographical area. Accordingly, theeSIM profile as downloaded by the user device may enable the user deviceto obtain telecommunication services from a wireless carrier networkoperated by the MNO or the partner MNO. The list of preferred RSPplatforms may be organized in an order of preference, e.g., from a mostpreferred RSP platform to a least preferred RSP platform. The LPAapplication of the user device may be further equipped with a list ofpredetermined service parameters for an ideal RSP platform. In someinstances, an eSIM management platform of the MNO may distribute thelist of preferred RSP platforms to the user device via a pull-model or apush-model. In various embodiments, the eSIM management platform is abackend service of the MNO that serves as an interface between the MNOand the RSP platforms.

Thus, when the user device relocates to the geographical area, the LPAapplication may request from the MRI platform the service features ofthe RSP platforms that are on the list of preferred RSP platforms. TheLPA application then compares the service features of each RSP platformthat are received from the MRI platform with the list of predeterminedservice parameters. For example, the service parameters may dictateminimal requirements for reliability, responsiveness, availability,functionality, etc. Based on the comparison, the LPA application maydetermine for each RSP platform the number of service parameters thatare met by the service features of the RSP platform. In this way, theLPA application may identify one or more candidate RSP platforms thatmeet a highest number of service parameters. If only a single candidateRSP platform is able to meet the highest number of service parameters,the LPA application may select the single RSP platform as a provider RSPplatform of the eSIM profile. Subsequently, the LPA application mayobtain an eSIM profile for accessing the telecommunication services ofthe MNO or the partner MNO from the provider RSP platform.

However, when multiple candidate RSP platforms meet the highest numberof service parameters, the LPA application may select one of themultiple RSP platforms that is indicated by the list of preferred RSPplatforms as being the most preferred as a provider RSP platform of theeSIM profile. Alternatively, or concurrently, one or more of thepredetermined service parameters may be designated as compulsive, suchthat a particular RSP platform must meet the one or more predeterminedservice parameters to be considered by the LPA application as acandidate RSP platform. Otherwise, the LPA application may reject theparticular RSP platform regardless of the overall number of serviceparameters that are met by the particular RSP platform.

The use of the MRI platform that is able to distribute informationregarding the service features of RSP platforms may provide an LPAapplication of a user device with the ability to autonomously select anRSP platform that best suits the eSIM profile operation needs of theuser device. Nevertheless, the eSIM management platform of the MNO isable to maintain some degree of control over which RSP platforms arepermitted to supply user devices with eSIM profiles via the distributionof RSP platform lists. Moreover, by offloading some of the dataaggregation and data analysis regarding the most appropriate RSPplatforms for distribution of eSIM profiles to the user devices and theMRI platform, the eSIM management platform may lessen its computationload and use its available computing resources to perform other eSIMprofile operations. The techniques described herein may be implementedin a number of ways. Example implementations are provided below withreference to the following FIGS. 1-6.

Example Architecture

FIG. 1 illustrates an example architecture 100 for a meta remote SIMprovisioning (RSP) platform to distribute information on servicefeatures of various RSP platforms to a user device such that the userdevice selects one of the RSP platforms as a provider of an eSIMprofile. In various embodiments, the user device 102 may be a consumerdevice. Consumer devices are network-capable devices that are generallymarketed to individual consumers. For example, these devices may includea smartphone, a tablet computer, a smartwatch, a gaming console, and/orso forth. The user device 102 may be capable of obtainingtelecommunication and/or data communication services from the mobilenetwork operator (MNO) 104. The MNO 104 may provide a wide range ofmobile communication services, as well as ancillary services andfeatures, to subscribers and associated mobile device users. In variousembodiments, the MNO 104 may provide a wireless carrier network thatserves multiple user devices. The wireless carrier network may alsorelay communications between the multiple user devices and user devicesthat are serviced by other telecommunications networks. Thetelecommunication services provided may include voice communication,multimedia communication, data communication, such as email, messaging,content streaming, content uploading, and/or so forth.

The wireless carrier network of the MNO 104 may be implemented usingmultiple interconnected networks. In various embodiments, the wirelesscarrier network may include multiple Radio Access Networks (RANs). TheRANs may be connected to each other via regional ground networks. Inturn, the regional ground networks may be connected to a core network bya wide area network (WAN). Each regional portion of the MNO 104 mayinclude one or more RANs and a regional circuit and/or packet-switchednetwork and associated signaling network facilities. The MNO 104 mayprovide telecommunication services in accordance with one or moretechnical standards, such as Enhanced Data Rates for GSM Evolution(EDGE), Wideband Code Division Multiple Access (W-CDMA), High SpeedPacket Access (HSPA), Long Term Evolution (LTE), CDMA-2000 (CodeDivision Multiple Access 2000), 5th Generation (5G), and/or so forth. Insome embodiments, the core network of the MNO 104 may be accessed viawired or wireless local area networks (LANs). For example, a wirelesslocal area network may be a network that is established using Wi-Fi orBluetooth standards and hardware. In various embodiments, the MNO 104provides a home wireless carrier network to the user device 102. Forexample, the user device 102 may be registered with the MNO 104, and thewireless carrier network of the MNO 104 is the default provider oftelecommunication services to the user device 102.

However, the user device 102 may from time to time obtaintelecommunication service from other wireless carrier networks that arepartner MNOs of the MNO 104, such as a partner MNO 106. The partner MNOsgenerally operate wireless carrier networks in geographical areas thatare not served by the MNO 104. For example, the wireless carrier networkprovided by the MNO 104 may lack telecommunication network coverage in aparticular geographical area. As a result, the MNO 104 may have one ormore partner MNOs that do provide telecommunication network coverage inthe particular geographical area. For example, the MNO 104 may operate aU.S. wireless carrier network, and a partner MNO of the MNO 104 mayoperate a European wireless carrier network. Nevertheless, in someinstances, the MNO 104 and the partner MNOs may operate wireless carriernetworks that have overlapping telecommunication network coverage.

The user device 102 may use an eSIM profile 108 that is stored in anembedded Subscriber Identity Module (eSIM) 110 of the user device 102 toauthenticate to the MNO 104 in order to obtain telecommunicationservices from the MNO 104. For example, the eSIM profile 108 may containa unique international mobile subscriber identity (IMSI) number thatauthenticates the user device 102 to the MNO 104. Other data that arestored in the eSIM profile may include carrier network information,security authentication information, a list of accessible networkservices, and/or so forth, that are specific to the MNO 104. An eSIMprofile that designates a wireless carrier network of a particular MNOas a home carrier network is referred to as an MNO-specific eSIM profileof that particular MNO. Accordingly, the eSIM profile 108 is anMNO-specific eSIM profile of the MNO 104. Nevertheless, in mostinstances, the eSIM profile 108 is also configured to enable the userdevice 102 to roam on the wireless carrier networks of the partner MNOs.

In some embodiments, a local profile assistant (LPA) application 112 onthe user device 102 may be configured to download a particular eSIMprofile associated with a partner MNO, such as the partner MNO 106. Insuch embodiments, the download of the eSIM profile may occur when theuser device 102 moves to a geographical area that is served by thewireless carrier network of the partner MNO and unserved by the wirelesscarrier network of the MNO 104. Accordingly, the particular eSIM profilemay enable the user device 102 to obtain optimal network performancefrom the wireless carrier network provided by the partner MNO. In someinstances, the use of the particular eSIM profile by the user device 102may also enable a subscriber associated with the user device 102 to paya discounted rate for the telecommunication services provided by thepartner MNO. For example, the discounted rate may be less than a roamingrate that would be otherwise paid by the subscriber for having the userdevice 102 roam on the wireless carrier network of the partner MNO viathe eSIM profile 108.

The user device 102 may download eSIM profiles associated with variousMNOs from multiple RSP platforms. For example, an RSP platform may sendone or more data packets that contain an eSIM profile to a modem of theuser device 102 via an over-the-air (OTA) update. The data packets areassembled by the software of the modem into the eSIM profile and loadedinto the eSIM 110 of the user device 102. In various embodiments, eachof the multiple RSP platforms may be responsible for the management ofeSIM profiles that are specific to one or more MNOs. Accordingly, eachof the RSP platforms may include one or more subscription managers thatare executed by one or more computing devices. In some embodiments, eachof the RSP platforms may include at least one Subscription Manager DataPreparation (SM-DP), at least one Subscription Manager Data PreparationPlus (SM-DP+), and at least one Subscription Manager Secure Routing(SM-SR).

In various embodiments, the eSIM profiles for user devices, such as theuser device 102, may be loaded into profile state stores of an SM-DP+operated by an RSP platform. In some instances, each profile data storeof the SM-DP+ may hold consumer eSIM profiles of a single MNO. In otherinstance, a single profile data store of an SM-DP+ may hold eSIMprofiles of multiple different MNOs. Accordingly, each SM-DP+ isresponsible for managing the eSIM profiles of a different MNO, ormultiple SM-DP+s can collectively manage eSIM profiles of a single MNO.Thus, the SM-DP+s may distribute eSIM profiles to the user devices inresponse to requests from the user devices.

The MRI platform 114 may be operated by a consortium of RSP platforms.In some instances, the consortium may be a collective of RSP platformsthat are designated by the MNO 104 to provide eSIM profiles to userdevices that are registered with the MNO 104 in various geographicalareas. For example, the group of RSP platforms 116(1)-116(K) maydistribute eSIM profiles for the partner MNO 106 that serves aparticular geographical area. Each of the eSIM profiles that areprovided by the RSP platforms 116(1)-116(K) may include carrier networkinformation, security authentication information, a list of accessiblenetwork services, and/or so forth, that are specific to the partner MNO106. Likewise, the consortium may include other groups of RSP platformsthat distribute eSIM profiles for MNOs that provide telecommunicationnetwork coverage in other geographical areas.

The MRI platform 114 may collect information on the service features ofthe RSP platforms in the consortium. The service features of an RSPplatform may include a geographical area serviced by the RSP platform,an availability of the RSP platform to distribute eSIM profiles, arepresentative (e.g., average) response time of the RSP platform torequests for eSIM profiles, a reliability rating of the RSP platform indistributing eSIM profiles, available inventory quantities of eSIMprofiles for different user device types that are carried by the RSPplatform, and/or so forth. Other service features of an RSP platform mayinclude the ability of the RSP platform to provide prioritizedprovisioning of eSIM profiles to a selective group of user devices thatbelong to a particular organization, an ability for the RSP platform toservice specialized eSIM profile management operations requested by theMNO 104 or an organization serviced by the MNO 104 (e.g., eSIM profileduplication, encryption, etc.), and an ability for the RSP platform tosupply customized eSIM profile (e.g., eSIM profiles that allow storageof additional client data within the profiles). For example, the MRIplatform 114 may collect service feature data 118(1) from the RSPplatform 116(1), service feature data 118(2) from the RSP platform116(2), and service feature data 118(3) from the RSP platform 116(3). Inturn, the MRI platform 114 may distribute the information on the servicefeatures of the RSP platforms 116(1)-116(K) to the LPA applications ofthe user devices.

In some embodiments, the eSIM 110 of the user device 102 may contain apreferred RSP platform file 120 that includes different lists ofpreferred RSP platforms for different geographical areas. In variousembodiments, an eSIM management platform of the MNO 104 may distributethe preferred RSP platform file 120 to the user device 102 via apull-model or a push-model. In the pull-model, the LPA application 112is configured to periodically request an updated version of thepreferred RSP platform file 120 from the eSIM management platform forstorage in the eSIM 110. In the push-model, the eSIM management platformmay periodically send the most updated version of the preferred RSPplatform file 120 to the LPA application 112. In turn, the LPAapplication 112 may store the most updated version in the eSIM 110. Eachlist of preferred RSP platforms for a corresponding geographical areamay be organized in an order of preference, e.g., from a most preferredRSP platform to a least preferred RSP platform. The user device 102 mayinitially access telecommunication services from the MNO 104 using theeSIM profile 108 that is specific to the MNO 104 while the user device102 is located in a first geographical area. Subsequently, the LPAapplication 112 may detect that the user device 102 has moved to asecond geographical area. The second geographical area may be an areathat is not covered by the wireless carrier network of the MNO 104, butwhich is covered by the wireless carrier network of the partner MNO 106.

Following such detection, the LPA application 112 may retrieve aparticular list of preferred RSP platforms that corresponds to thesecond geographical area from the preferred RSP platform file 120. TheLPA application 112 may then request from the MRI platform 114information on the service features of the RSP platforms that are on theparticular list. In response, the MRI platform 114 may send the requestinformation as aggregated service feature data 122 to the LPAapplication 112. The LPA application 112 compares the service featuresof each RSP platform that are received from the MRI platform 114 with apredetermined service parameters list 124. For example, the serviceparameters may dictate minimal requirements for reliability,responsiveness, availability, functionality, etc. that are set by theMNO 104 for the user device 102.

Based on the comparison, the LPA application 112 may determine for eachRSP platform the number of service parameters that are met by theservice features of the RSP platform. In this way, the LPA application112 may identify one or more candidate RSP platforms that meet a highestnumber of service parameters. If only a single candidate RSP platform isable to meet the highest number of service parameters, the LPAapplication 112 may select the single RSP platform as a provider RSPplatform of an eSIM profile to user device 102. Subsequently, the LPAapplication 112 may obtain an eSIM profile for using thetelecommunication services of the partner MNO 106 from this provider RSPplatform. For example, if the LPA application 112 selects the RSPplatform 116(K) as the provider RSP platform, the LPA application 112may send an eSIM profile request 126 to the RSP platform 116(K). Inresponse, the RSP platform 116(K) may send an eSIM profile 128 that isspecific for the partner MNO 106 to the user device 102 for storage inthe eSIM 110. The eSIM profile 128 is then used by the user device 102to access telecommunication services from the partner MNO 106 while theuser device 102 is in the second geographical area. In some instances,there may be an error scenario in which the initial provider RSPplatform is unable to distribute an eSIM profile to the user device 102in a predetermined amount of time. In such an error scenario, the LPAapplication 112 may request the eSIM profile from an RSP platform thatmeets the next highest number of service parameters, and so on. In thisway, the LPA application 112 may repeat such a procedure for any furthererror scenarios until the user device 102 is provisioned with an eSIMprofile by an RSP platform.

However, when multiple candidate RSP platforms are identified by the LPAapplication 112 as meeting the highest number of service parameters, theLPA application 112 may determine which of these multiple candidate RSPplatforms is indicated by the particular list of preferred RSP platformsas being the most preferred RSP platform. The most preferred RSPplatform of these multiple candidate RSP platforms is then selected bythe LPA application 112 as a provider RSP platform of the eSIM profile.Once again, if the LPA application 112 selects the RSP platform 116(K)as the provider RSP platform, the LPA application 112 may send an eSIMprofile request 126 to the RSP platform 116(K). In response, the RSPplatform 116(K) may distribute an eSIM profile 128 that is specific forthe partner MNO 106 to the user device 102 for storage in the eSIM 110.

In some instances, there may be an error scenario in which the mostpreferred RSP platform that meets the highest number of serviceparameters is unable to distribute an eSIM profile to the user device102 in a predetermined amount of time. In such an error scenario, theLPA application 112 may request the eSIM profile from an RSP platformthat is the next most preferred RSP platform that meets the highestnumber of service parameters. If such an error scenario occurs with allof the RSP platforms that meet the highest number of service parameters,then the LPA application 112 may request the eSIM profile from an RSPplatform that meets the next highest number of service parameters and isalso most preferred on the particular list of preferred RSP platforms,and so on and so forth. In this way, the LPA application 112 may repeatsuch a procedure for any further error scenarios until the user device102 is provisioned with an eSIM profile by an available RSP platform.

In alternative embodiments, one or more of the predetermined serviceparameters included in the service parameters list 124 may be designatedas compulsive. This means that a particular RSP platform in a list ofpreferred RSP platforms must meet the one or more predetermined serviceparameters in order to be considered by the LPA application 112 as acandidate RSP platform. Otherwise, the LPA application 112 may rejectthe particular RSP platform as a candidate RSP platform regardless ofthe overall number of service parameters that are met by the particularRSP platform. In the case of such a rejection, the LPA application 112may select an equivalently preferred or the next most preferred RSPplatform that does meet every compulsive service parameter as theprovider RSP platform.

In additional embodiments, the LPA application 112 may perform asimplified procedure for selecting a candidate RSP platform. In suchembodiments, the user device 102 may initially access telecommunicationservices from the MNO 104 using the eSIM profile 108 that is specific tothe MNO 104 while the user device 102 is located in a first geographicalarea. Subsequently, the LPA application 112 may detect that the userdevice 102 has moved to a second geographical area. The secondgeographical area may be an area that is not covered by the wirelesscarrier network of the MNO 104, but which is covered by the wirelesscarrier network of the partner MNO 106.

Following such detection, the LPA application 112 may request a list ofavailable RSP platforms for the second geographical area from the MRIplatform 114. Further, the LPA application 112 may retrieve a particularlist of preferred RSP platforms that corresponds to the secondgeographical area from the preferred RSP platform file 120.Subsequently, the LPA application 112 may compare the list of availableRSP platforms to the particular list of preferred RSP platform todetermine an available RSP platform that is also designated as the mostpreferred RSP platform in the particular list of preferred RSPplatforms. Accordingly, the LPA application 112 may obtain an eSIMprofile from this available RSP platform. For example, if the RSPplatform 116(K) is available and is the most preferred RSP platform, theLPA application 112 may send the eSIM profile request 126 to the RSPplatform 116(K). In response, the RSP platform 116(K) may provide theeSIM profile 128 that is specific for the partner MNO 106 to the userdevice 102 for storage in the eSIM 110. The eSIM profile 128 is thenused by the user device 102 to access telecommunication services fromthe partner MNO 106 while the user device 102 is in the secondgeographical area.

In some instances, there may be an error scenario in which the mostpreferred and available RSP platform is unable to distribute an eSIMprofile to the user device 102 in a predetermined amount of time. Insuch an error scenario, the LPA application 112 may request the eSIMprofile from another available RSP platform that is the next mostpreferred RSP platform designated in the particular list of preferredRSP platforms, and so on and so forth. In this way, the LPA application112 may repeat such a procedure for any further error scenarios untilthe user device 102 is provisioned with an eSIM profile by an availableRSP platform.

In the above embodiments, the LPA application 112 is described as makinguse of the Mill platform 114 when the user device 102 moves from a firstgeographical area that is served by the MNO 104 to a second geographicalarea that is unserved by the MNO 104 and served by the partner MNO 106.However, in other embodiments, the LPA application 112 may make use ofthe MRI platform 114 to obtain an eSIM profile in a similar manner whenthe user device 102 needs to initially request the eSIM profile toobtain telecommunication services from the MNO 104. In additionalembodiments, the LPA application 112 may also make use of the MMplatform 114 to obtain a new eSIM profile in a similar manner when theuser device 102 moves between geographical areas that are served bywireless carrier networks that belong to different partner MNOs of theMNO 104.

Example MRI Platform

FIG. 2 is a block diagram showing various components of one or moreillustrative computing devices that support the MRI platform 114. Thecomputing devices 200 may include a communication interface 202, one ormore processors 204, memory 206, and hardware 208. The communicationinterface 202 may include wireless and/or wired communication componentsthat enable the computing devices 200 to transmit data to and receivedata from other networked devices. The hardware 208 may includeadditional user interfaces, data communication, or data storagehardware. For example, the user interfaces may include a data outputdevice (e.g., visual display, audio speakers), and one or more datainput devices. The data input devices may include, but are not limitedto, combinations of one or more of keypads, keyboards, mouse devices,touch screens that accept gestures, microphones, voice or speechrecognition devices, and any other suitable devices.

The memory 206 may be implemented using computer-readable media, such ascomputer storage media. Computer-readable media includes, at least, twotypes of computer-readable media, namely computer storage media andcommunications media. Computer storage media includes volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD), high-definition multimedia/data storage disks, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transmissionmedium that can be used to store information for access by a computingdevice. In contrast, communication media may embody computer-readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave, or other transmissionmechanisms. In other embodiments, the computing devices 200 orcomponents thereof may be virtual computing devices in the form ofvirtual machines or software containers that are hosted in a computingcloud.

The computing devices 200 may implement the MRI platform 114. Theimplementation involves the execution of software, applications, and/ormodules that include routines, program instructions, code segments,objects, and/or data structures that perform particular tasks orimplement particular abstract data types. The Mill platform 114 mayinclude an interface module 210, a collection module 212, and adistribution module 214.

The interface module 210 may enable the Mill platform 114 to communicatewith RSP platforms, such as the RSP platforms 116(1)-116(K) via astandard protocol, such as the Hypertext Markup Language Protocol (HTTP)or the Hypertext Transfer Protocol Secure (HTTPS). In some instances,the interface module 210 may call one or more APIs of an RSP platform todownload the service feature data for the RSP platform. Alternatively,or concurrently, the interface module 210 may include one or more APIsthat are callable by an RSP platform that wants to provide its servicefeature data to the MRI platform 114. In some embodiments, the interfacemodule 210 may include an authentication function that controls RSPplatform access to the MRI platform 114. For example, an interfacefunction of each RSP platform may submit a corresponding authenticationcredential to the interface module 210 when the RSP platform initiallyregisters with the Mill platform 114. For example, the authenticationcredential may include an RSP identifier and a unique authenticationtoken. The authentication credential of each RSP platform is stored bythe MRI platform 114 in an authentication credential data store 216.Accordingly, the interface function of an RSP platform may submit anauthentication credential in order to interface with the MRI platform114. In turn, the MRI platform 114 may validate the submittedauthentication credential against the stored authentication credentialfor the RSP platform to determine whether the RSP platform is to begranted interface access. In various embodiments, the computing devicesof the MRI platform 114 and the RSP platforms may communicate via anetwork. The network may include a wireless carrier network, a localarea network (LAN), a wide area network (WAN), and/or so forth.

The collection module 212 may store the received service feature data ofthe RSP platforms in a service feature data store 218. In variousembodiments, the service feature data store 218 may include one or moredatabases, such as relational databases, object databases,object-relational databases, and/or key-value databases that store data.The service feature data for each RSP platform may be stored as relateddata entries in the one or more databases. Thus, as the interface module210 receives updated service feature data from an RSP platform, thecollection module 212 may update one or more data entries in thedatabases with the most recent information. In some embodiments, thecollection module 212 may periodically activate the interface module 210to poll servers of the RSP platforms for service feature data. In otherembodiments, the servers of the RSP platform may periodically upload theservice feature data to the MRI platform 114 via the interface module210.

The distribution module 214 may receive requests from the LPAapplications of user devices for service feature data of RSP platforms.For example, an LPA application may request service feature data of RSPplatforms that appear in a list of preferred RSP platforms for aparticular geographical area. The request from a particular LPAapplication may include information such as the identifiers of the RSPplatforms, the corresponding geographical areas serviced by the RSPplatforms, a timestamp for the initiation of the request, and/or so. Inturn, the distribution module 214 may retrieve the requested informationof the RSP platforms from the service feature data store 218, aggregatethe information into aggregated service feature data, and send theaggerate service feature data to the particular LPA application via thenetwork. In some instances, one or more RSP platforms that are includedin the request from the LPA application may be unavailable to providethe eSIM profile. Accordingly, the distribution module 214 may return noservice feature data for these RSP platforms. Rather, the distributionmodule 214 may indicate to the LPA application that these RSP platformsare not available.

In some instances, the request from an LPA application may furtherinclude an authentication credential of the LPA application. In suchinstances, the distribution module 214 may validate the authenticationcredential included in the request against a pre-stored authenticationcredential of the LPA application in the authentication credential datastore 216. Accordingly, if the authentication credentials match, thedistribution module 214 may fulfill the request. However, if theauthentication credentials do not match, the distribution module 214 maydeny the request. In other embodiments, the distribution module 214 mayinstead receive a request for a list of RSP platforms in a geographicalarea that are available to provide eSIM profiles on behalf of thepartner MNO. In turn, the distribution module 214 may return the list ofone or more available RSP platforms to the LPA application via thenetwork.

Example Computing Device Components

FIG. 3 is a block diagram showing various components of an illustrativeuser device that interfaces with the meta RSP platform. The user device102 may include a communication interface 302, one or more sensors 304,a user interface 306, one or more processors 308, memory 310, and devicehardware 312. The communication interface 302 may include wirelessand/or wired communication components that enable the electronic deviceto transmit or receive voice or data communication via the wirelesscarrier network, as well as other telecommunication and/or datacommunication networks. The sensors 304 may include a proximity sensor,a compass, an accelerometer, biometric sensors, cameras, and/or a globalpositioning system (GPS) sensor, among other appropriate sensors. Theproximity sensor may detect the movement of objects that are proximateto the user device 102. The compass, the accelerometer, and the GPSsensor may detect orientation, movement, and geolocation of the userdevice 102. The cameras may capture images of the environment around theuser device 102.

The user interface 306 may enable a user to provide inputs and receiveoutputs from the user device 102. The user interface 306 may include adata output device (e.g., visual display, audio speakers), and one ormore data input devices. The data input devices may include, but are notlimited to, combinations of one or more of keypads, keyboards, mousedevices, touch screens, microphones, speech recognition packages, andany other suitable devices or other electronic/software selectionmethods.

The memory 310 may be implemented using computer-readable media, such ascomputer storage media. Computer-readable media includes, at least, twotypes of computer-readable media, namely computer storage media andcommunications media. Computer storage media includes volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other non-transmission medium that can be used to storeinformation for access by a computing device. In contrast, communicationmedia may embody computer-readable instructions, data structures,program modules, or other data in a modulated data signal, such as acarrier wave, or other transmission mechanisms.

The device hardware 312 may include a cellular modem that enables theuser device 102 to perform telecommunication and data communication withone or more wireless carrier networks, as well as a short-rangetransceiver that enables the device to connect to other devices viashort-range wireless communication links. The device hardware 312 mayfurther include signal converters, antennas, hardware decoders andencoders, graphics processors, and/or the like that enable the userdevice 102 to execute applications and provide telecommunication anddata communication functions. The cellular modem may be driven by modemsoftware to perform telecommunication and data communication with awireless communication network. The modem software may be firmware thatis stored in dedicated non-volatile memory of the user device 102. Suchnon-volatile memory may include read-only memory (ROM), erasableprogrammable read-only memory (EPROM), or flash memory. The user deviceis further equipped with the eSIM 110 that stores one or more eSIMprofiles.

The one or more processors 308 and the memory 310 of the user device 102may implement an operating system 314, device software 316, one or moreapplications 318, and the LPA application 112. Such software may includeroutines, program instructions, objects, and/or data structures that areexecuted by the processors 308 to perform particular tasks or implementparticular abstract data types.

The operating system 314 may include components that enable the userdevice 102 to receive and transmit data via various interfaces (e.g.,user controls, communication interface 302, and/or memory input/outputdevices). The operating system 314 may also process data using the oneor more processors 308 to generate outputs based on inputs that arereceived via the user interface 306. For example, the operating system314 may provide an execution environment for the execution of theapplications 318. The operating system 314 may include a presentationcomponent that presents the output (e.g., display the data on anelectronic display, store the data in memory, transmit the data toanother electronic device, etc.).

The operating system 314 may include an interface layer that enablesapplications to interface with the modem and/or the communicationinterface 302. The interface layer may comprise public APIs, privateAPIs, or a combination of both public APIs and private APIs.Additionally, the operating system 314 may include other components thatperform various other functions generally associated with an operatingsystem. The device software 316 may include software components thatenable the user device to perform functions. For example, the devicesoftware 316 may include basic input/output system (BIOS), bootrom, or abootloader that boots up the user device 102 and executes the operatingsystem 314 following power-up of the device.

The applications 318 may include applications that provide utility,entertainment, and/or productivity functionalities to a user of the userdevice 102. For example, the applications 318 may include telephonyapplications, electronic mail applications, remote desktop applications,web browser applications, navigation applications, office productivityapplications, multimedia streaming applications, an online shoppingapplication, and/or so forth.

The LPA application 112 may include a platform update module 320, arequest module 322, a comparison module 324, and a download module 326.Such modules may include routines, program instructions, objects, and/ordata structures that are executed by the processors 204 to performparticular tasks or implement particular abstract data types. The LPAapplication 112 may communicate with one or more computing devices ofthe MRI platform via a network. The network may include a wirelesscarrier network, a local area network (LAN), a wide area network (WAN),and/or so forth.

The platform update module 320 may obtain preferred RSP platform files,such as the preferred RSP platform file 120, from an eSIM managementplatform of the MNO 104 via a pull-model or a push-model. In thepull-model, the platform update module 320 may periodically request anupdated version of the preferred RSP platform file 120 from the eSIMmanagement platform for storage in the eSIM 110. In the push-model, theeSIM management platform may periodically send the most updated versionof the preferred RSP platform file 120 to the platform update module320. In turn, the platform update module 320 may store the most updatedversion in the eSIM 110.

The request module 322 may request information on the service featuresof one or more particular RSP platforms that serve a geographical areafrom the MRI platform 114. In some embodiments, the request module 322may initiate a request when the user device 102 determines viageolocation data that the user device 102 has moved to a newgeographical area. However, in other embodiments, the request module 322may initiate the request when the user device 102 initially powers upwhile located in a geographical area. The particular RSP platforms maybe platforms that are designated as preferred RSP platforms by a list ofpreferred RSP platforms that corresponds to the geographical area. Inresponse to a request, the MRI platform 114 may send the information asaggregated service feature data to the request module 322. The servicefeatures of an RSP platform may include a geographical area serviced bythe RSP platform, an availability of the RSP platform to distribute eSIMprofiles, a representative response time of the RSP platform to requestsfor eSIM profiles, a reliability rating of the RSP platform indistributing eSIM profiles, available inventory quantities of eSIMprofiles for different user device types that are carried by the RSPplatform, and/or so forth.

The availability of the RSP platform may be measured via a ratio of anumbers of times that the RSP platform responded to eSIM profilerequests within a predetermined time limit to a number of times that theRSP platform responded to eSIM profile requests outside of thepredetermined time limit. The RSP platform is considered to haveresponded to an eSIM request when the RSP platform provides an eSIMprofile to a user device in response to the request. Such a ratio may becomputed for a predetermined time period. The predetermined time periodmay be an active lifetime of the RSP platform, a periodic time interval(first quarter, second quarter, etc.), or a moving window of time (e.g.,the most recent 60 days). The representative response time (e.g., 600milliseconds) of the RSP platform may be a mean, median, or mode of theresponse times of the RSP platform in a given time period. The giventime period may be an active lifetime of the RSP platform, a periodictime interval (first quarter, second quarter, etc.), or a moving windowof time (e.g., the most recent 60 days).

The reliability of RSP platform may be measured by a percentage of timesthat the RSP platform responded to eSIM profile requests within amaximum timeout limit during a specific time period. The failure of theRSP platform to respond to the SIM profile request within the maximumtimeout limit is considered to be a failure to respond. The specifictime period may be an active lifetime of the RSP platform, a periodictime interval (first quarter, second quarter, etc.), or a moving windowof time (e.g., the most recent 60 days). In alternative embodiments, thereliability of the RSP platform may be measured by a number of timesthat the RSP platform responded to eSIM profile requests within amaximum timeout limit during a specific time period. An availabilityinventory quantity of eSIM profiles for a particular user device typemay refer to the number of the eSIM profiles stored by an RSP platformthat are available for distribution to user devices.

Other service features of an RSP platform may include the ability of theRSP platform to provide prioritized provisioning of eSIM profiles to aselective group of user devices that belong to a particularorganization, an ability for the RSP platform to service specializedeSIM profile management operations requested by the MNO or anorganization serviced by the MNO (e.g., eSIM profile duplication,encryption, etc.), an ability for the RSP platform to supply customizedeSIM profiles (e.g., eSIM profiles that allow storage of additionalclient data within the profiles). In alternative embodiments, therequest module 322 may be configured to simply request a list of RSPplatforms in a geographical area that are available to provide eSIMprofiles on behalf of the partner MNO. In turn, the MRI platform 114 mayreturn the list of one or more available RSP platforms to the LPAapplication via the network.

The comparison module 324 may compare the received service feature dataof each RSP platform to a service parameters list that is stored in thememory 310 of the user device 102, such as the service parameters list124. For example, the service parameters may dictate minimalrequirements for an availability of the RSP platform to distribute eSIMprofiles, an average response time of the RSP platform to requests foreSIM profiles, a reliability rating of the RSP platform in distributingeSIM profiles, available inventory quantities of eSIM profiles fordifferent user device types that are carried by the RSP platform, and/orso forth. The service parameters may also dictate whether an RSPplatform must have the ability to provide prioritized provisioning ofeSIM profiles to a selective group of user devices that belong to aparticular organization, the ability for the RSP platform to servicespecialized eSIM profile management operations requested by the MNO oran organization serviced by the MNO (e.g., eSIM profile duplication,encryption, etc.), and the ability for the RSP platform to supplycustomized eSIM profile (e.g., eSIM profiles that allow storage ofadditional client data within the profiles). In some embodiments, thecomparison module 324 may receive a single service parameters list fromthe eSIM management platform of the MNO 104, in which such a list is tobe used regardless of geographical area. However, in other embodiments,the eSIM management platform of the MNO 104 may provide the comparisonmodule 324 with multiple service parameters lists for use with respectto different geographical areas.

The comparison module 324 may compare the service features of an RSPplatform to a service parameters list to determine whether the RSPplatform qualifies as a candidate RSP platform for supplying an eSIMprofile to the user device 102. During the comparison, the comparisonmodule 324 may determine for each RSP platform the number of serviceparameters that are met by the service features of the RSP platform. Inthis way, the comparison module 324 may identify one or more candidateRSP platforms that meet a highest number of service parameters. If onlya single candidate RSP platform is able to meet the highest number ofservice parameters, the comparison module 324 may select the single RSPplatform as a provider RSP platform of the eSIM profile. However, whenmultiple candidate RSP platforms are meeting the highest number ofservice parameters, the comparison module 324 may select one of themultiple RSP platforms that is indicated by the list of preferred RSPplatforms as being the most preferred as a provider RSP platform of theeSIM profile.

In some embodiments, one or more of the service parameters in theservice parameters list may be designated as compulsive, such that aparticular RSP platform must meet the one or more predetermined serviceparameters to be considered by the comparison module 324 as a candidateRSP platform. Otherwise, the comparison module 324 may reject theparticular RSP platform as a candidate RSP platform regardless of theoverall number of service parameters that are met by the particular RSPplatform.

In alternative embodiments, the request module 322 may receive a list ofone or more available RSP platforms in response to a request for RSPplatforms in a geographical area that are able to provide eSIM profileson behalf of a partner MNO. In such embodiments, the comparison module324 may compare the list of one or more available RSP platforms to thelist of preferred RSP platforms. In this way, the comparison module 324may select an available RSP platform that is also the most preferred asthe provider RSP platform.

The download module 326 may be configured to send an eSIM profilerequest to a provider RSP platform that is selected by the comparisonmodule 324. The eSIM profile request may include a device identifier ofthe user device 102, an identifier of the eSIM 110, a network identifierof the MNO 104, i.e., home carrier network, geolocation information ofthe user device 102, a network identifier of the MNO for which the eSIMprofile is being sought, and/or other identification information. Inturn, the RSP platform may prepare and send an eSIM profile that isspecific for the partner MNO 106 to the user device 102. Further, theRSP platform may activate a billing function of the partner MNO 106,such as an Online Charging System (OCS) or another equivalent corenetwork component, to track the usage of telecommunication services bythe user device 102. The tracked usage information is used by thebilling function to bill a subscriber account established for the userdevice 102 or pass through the charges to a subscriber account that isassociated with the user device 102 and established with the MNO 104.

The eSIM profile is stored by the download module 326 into the eSIM 110.The eSIM profile is then used by the user device 102 to accesstelecommunication services from the partner MNO 106. In some instances,the storage of the eSIM profile that is specific to partner MNO 106(e.g., eSIM profile 128) into the eSIM 110 may include a replacement ofan existing eSIM profile (e.g., eSIM profile 108 that is specific to theMNO 104) in the eSIM 110. However, in other instances, the eSIM profilethat is specific to partner MNO 106 may be stored in the eSIM 110 alongwith an existing eSIM profile. In some embodiments, the download module326 may send a notification to the comparison module 324 when theprovider RSP platform is unable to provide the eSIM profile is apredetermined amount of time. In response to the notification, thecomparison module 324 may select another candidate RSP platform as theprovider RSP platform as specified with respect to the error scenariosdescribed in FIG. 1.

Example Processes

FIGS. 4-6 present illustrative processes 400-600 for an MRI platform todistribute information regarding RSP platforms to the LPA applicationsof user devices, such that the user device selects one of the RSPplatforms as a provider of an eSIM profile. Each of the processes400-600 is illustrated as a collection of blocks in a logical flowchart, which represents a sequence of operations that can be implementedin hardware, software, or a combination thereof. In the context ofsoftware, the blocks represent computer-executable instructions that,when executed by one or more processors, perform the recited operations.Generally, computer-executable instructions may include routines, codesegments, programs, objects, components, data structures, and the likethat perform particular functions or implement particular abstract datatypes. The order in which the operations are described is not intendedto be construed as a limitation, and any number of the described blockscan be combined in any order and/or in parallel to implement theprocess. For discussion purposes, the processes 400-600 are describedwith reference to the architecture 100 of FIG. 1.

FIG. 4 is a flow diagram of an example process 400 for using the metaRSP platform to identify a preferred RSP platform for downloading aneSIM profile of a partner mobile network operator (MNO). At block 402,the LPA application 112 on the user device 102 may receive a list ofpreferred RSP platforms that are designated by the MNO 104 to distributeeSIM profiles for a partner MNO that provides telecommunication servicesin a particular geographical area. In some instances, the user device102 may receive the list of preferred RSP platforms while accessing thetelecommunication services provided by the MNO 104 via the MNO-specificeSIM profile 108 stored in the eSIM 110 of the user device 102. Forexample, the user device 102 may be located in a current geographicalarea served by a wireless carrier network of the MNO 104. In otherinstances, the user device 102 may receive the list while usingtelecommunication services provided by an additional partner MNO of theMNO 104 using an eSIM profile that is specific to the additional partnerMNO. For example, the user device 102 may be located in a currentgeographical area served by a wireless carrier network of the additionalpartner MNO. In various embodiments, the list of preferred RSP platformsmay be provided by an RSP management function of the MNO 104. The listmay be organized in an order of preference, e.g., from a most preferredRSP platform to a least preferred RSP platform.

At block 404, the LPA application 112 may determine that the user device102 is in the particular geographical area. For example, the user device102 may have moved from the current geographical area to the particulargeographical area. In various embodiments, the LPA application 112 maymake this determination based on geolocation data detected by a GPSsensor of the user device 102. At block 406, the LPA application 112 mayobtain from the MRI platform 114 a list of available RSP platforms thatare able to distribute eSIM profiles for the partner MNO in theparticular geographical area. In response, the MRI platform 114 mayreturn the list of available of RSP platforms in response to a requestfrom the LPA application 112.

At block 408, the LPA application 112 may identify a most preferred RSPplatform in the list of available RSP platforms using the list ofpreferred RSP platforms. In various embodiments, the LPA application 112may compare the list of available RSP platforms and the list ofpreferred RSP platforms to identify the most preferred RSP platform.

At block 410, the LPA application 112 may download an eSIM profile ofthe partner MNO from the most preferred RSP platform. The download mayinclude the LPA application 112 requesting the eSIM profile from themost preferred RSP platform. In turn, the most preferred RSP platformmay send the eSIM profile to the user device 102. The downloaded eSIMprofile may be stored by the LPA application 112 in the eSIM 110 of theuser device 102. In some instances, the storage of the downloaded eSIMprofile of the partner MNO may include replacing an existing eSIMprofile stored in the eSIM 110 with the eSIM profile of the partner MNO.However, in other instances, the downloaded eSIM profile of the partnerMNO may be stored along with the existing eSIM profile in the eSIM 110.

At block 412, the user device 102 may access telecommunication servicein the particular geographical area from the partner MNO of the MNOusing the eSIM profile specific to the partner MNO. The user device 102is able to access a wireless carrier network of the partner MNO usingthe eSIM profile specific to the partner MNO.

FIGS. 5a and 5b illustrate a flow diagram of an example process 500 forusing the meta RSP platform to identify an RSP platform for downloadingan eSIM profile of a partner MNO based on the service features ofmultiple RSP platforms. At block 502, the LPA application 112 on theuser device 102 may receive a list of preferred RSP platforms that aredesignated by the MNO 104 to distribute eSIM profiles for a partner MNOthat provides telecommunication services in a particular geographicalarea. In some instances, the user device 102 may receive the list ofpreferred RSP platforms while accessing telecommunication servicesprovided by the MNO 104 via the MNO-specific eSIM profile 108 stored inan eSIM 110 of the user device 102. For example, the user device 102 maybe located in a current geographical area served by a wireless carriernetwork of the MNO 104. In other instances, the user device 102 mayreceive the list while accessing telecommunication services provided byan additional partner MNO of the MNO 104 via an eSIM profile that isspecific to the additional partner MNO. For example, the user device 102may be located in a current geographical area served by a wirelesscarrier network of the additional partner MNO. In various embodiments,the list of preferred RSP platforms may be provided by an RSP managementfunction of the MNO 104. The list may be organized in an order ofpreference, e.g., from a most preferred RSP platform to a leastpreferred RSP platform.

At block 504, the LPA application 112 may determine that the user device102 is in the particular geographical area. For example, the user device102 may have moved from the current geographical area to the particulargeographical area. In various embodiments, the LPA application 112 maymake this determination based on geolocation data detected by a GPSsensor of the user device 102. At block 506, the LPA application 112 mayobtain from the MRI platform 114 one or more service features ofindividual RSP platforms in the list of preferred RSP platforms. In someinstances, the MRI platform 114 may determine that one or more RSPplatforms in the list of preferred RSP platforms are no longer availableto distribute eSIM profiles for the partner MNO. Accordingly, the LPAapplication 112 may return the one or more service features ofindividual RSP platforms that are available.

At block 508, the LPA application 112 may determine a number of serviceparameters that are met by the one or more service features of theindividual platforms. In various embodiments, the service parameters maybe retrieved by the LPA application 112 from a service parameter listthat is stored in a memory of the user device 102.

At block 510, the LPA application 112 may identify one or more RSPplatforms that meet a highest number of service parameters. Thus, if theLPA application 112 determines that there is only a single RSP platformwith service features that meets the highest number of serviceparameters at decision block 512, the process 500 may proceed to block514. At block 514, the LPA application 112 may designate the single RSPplatform as a provider RSP platform. Subsequently, the process 500 mayproceed directly to block 518. However, if at the decision block 512 theLPA application 112 determines that there multiple RSP platforms thatmeet the highest number of service parameters, the process 500 mayproceed to block 516. At block 516, the LPA application 112 maydesignate one of the multiple RSP platforms that is indicated as mostpreferred by the list of preferred RSP platforms as the provider RSPplatform. Subsequently, the process 500 may proceed to block 518.

At block 518, the LPA application 112 may download an eSIM profile ofthe partner MNO from the provider RSP platform. The download may includethe LPA application 112 requesting the eSIM profile from the providerRSP platform. In turn, the provider RSP platform may send the eSIMprofile to the user device 102. The downloaded eSIM profile may bestored by the LPA application 112 in the eSIM 110 of the user device102. In some instances, the storage of the downloaded eSIM profile ofthe partner MNO may include replacing an existing eSIM profile stored inthe eSIM 110 with the eSIM profile of the partner MNO. However, in otherinstances, the downloaded eSIM profile of the partner MNO may be storedalong with the existing eSIM profile in the eSIM 110.

At block 520, the user device 102 may access telecommunication servicein the particular geographical area from the partner MNO of the MNOusing the eSIM profile of the partner MNO. The user device 102 is ableto access a wireless carrier network of the partner MNO using the eSIMprofile of the partner MNO.

FIG. 6 is a flow diagram of an example process 600 for distributinginformation on the service features of multiple RSP platforms to a localprofile assistant (LPA) application. At block 602, the MRI platform 114may receive information on service features of multiple RSP platforms.In some instances, the MRI platform 114 may call one or more APIs of anRSP platform to download the service feature data for the RSP platform.Alternatively, or concurrently, the MRI platform 114 may include one ormore APIs that are callable by an RSP platform that wants to provide itsservice feature data to the MRI platform 114. At block 604, the MRIplatform 114 may store the information on the service features of themultiple RSP platforms in a service feature data store of the MRIplatform 114.

At block 606, the MRI platform 114 may receive a request for informationon the service features of one or more RSP platforms from an LPAapplication of a user device. The request from the LPA application mayinclude query parameters such as the identifiers of the RSP platforms,the corresponding geographical areas serviced by the RSP platforms, atimestamp for the initiation of the request, and/or so. In turn, the MRIplatform 114 may retrieve the requested information of the one or moreRSP platforms from the service feature data store. At block 608, the MRIplatform 114 may send the requested information to the LPA application.

The use of the MRI platform that is able to distribute informationregarding the service features of RSP platforms may provide an LPAapplication of a user device with the ability to autonomously select anRSP platform that best suits the eSIM profile operation needs of theuser device. Nevertheless, the eSIM management platform of the MNO isable to maintain some degree of control over which RSP platforms arepermitted to supply user devices with eSIM profiles via the distributionof RSP platform lists. Moreover, by offloading some of the dataaggregation and data analysis regarding the most appropriate RSPplatforms for distribution eSIM profiles to the user devices and the MRIplatform, the eSIM management platform may lessen its computation loadand use its available computing resources to perform other eSIM profileoperations.

CONCLUSION

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. One or more non-transitory computer-readablemedia of a user device storing computer-executable instructions thatupon execution cause one or more processors to perform acts comprising:receiving a list of remote SIM provisioning (RSP) platforms that aredesignated by a mobile network operator (MNO) to distribute eSIMprofiles of a partner MNO of the MNO, the partner MNO providingtelecommunication services in a geographical area via a wireless carriernetwork; obtaining one or more service features of individual RSPplatforms in the list of RSP platforms from a meta RSP interface (MRI)platform in response to determining that the user device is in thegeographical area; determining a number of service parameters set by theMNO for the user device that are met by the one or more service featuresof the individual RSP platforms; and in response to identifying a singleRSP platform of the individual RSP platforms as meeting a highest numberof service parameters, requesting a download of an eSIM profile from thesingle RSP platform to access the telecommunication services from thewireless carrier network of the partner MNO.
 2. The one or morenon-transitory computer-readable media of claim 1, wherein the actsfurther comprise storing the eSIM profile received from the single RSPplatform in an eSIM of the user device.
 3. The one or morenon-transitory computer-readable media of claim 1, wherein each of oneor more compulsive service parameters included in the service parametersare met by a corresponding service feature included in one or moreservice features of the single RSP platform.
 4. The one or morenon-transitory computer-readable media of claim 1, wherein the actsfurther comprise requesting the download of the eSIM profile from an RSPplatform that meets a next highest number of service parameters inresponse to the single RSP platform being unable to provide the eSIMprofile in a predetermined period of time.
 5. The one or morenon-transitory computer-readable media of claim 1, wherein thedetermining that the user device is in the geographical area includesdetermining that the user device has moved from an additionalgeographical area to the geographical area, the additional geographicalarea being serviced by an additional wireless carrier network of the MNOor an additional partner MNO of the MNO.
 6. The one or morenon-transitory computer-readable media of claim 1, wherein the list ofRSP platforms lists the individual RSP platforms according to an orderof preference, further comprising: in response to identifying multipleRSP platforms of the individual RSP platforms as meeting the highestnumber of service parameters, requesting a download of the eSIM profilefrom one of the multiple RSP platforms that is indicated as a mostpreferred RSP platform by the list to access the telecommunicationservices from the wireless carrier network of the MNO.
 7. The one ormore non-transitory computer-readable media of claim 6, wherein the actsfurther comprise storing the eSIM profile received from the mostpreferred RSP platform in an eSIM of the user device.
 8. The one or morenon-transitory computer-readable media of claim 6, wherein each of oneor more compulsive service parameters included in the service parametersare met by a corresponding service feature included in one or moreservice features of the most preferred RSP platform.
 9. The one or morenon-transitory computer-readable media of claim 6, wherein the actsfurther comprise requesting the download of the eSIM profile from an RSPplatform that is indicated as a next most preferred RSP platform by thelist in response to the most preferred RSP platform being unable toprovide the eSIM profile in a predetermined period of time.
 10. The oneor more non-transitory computer-readable media of claim 1, wherein aservice feature of an RSP platform includes a geographical area servicedby the RSP platform, an availability of the RSP to distribute eSIMprofiles, a representative response time of the RSP platform to requestsfor the eSIM profiles, a reliability of the RSP platform in distributingthe eSIM profiles, or available inventory quantities of specific eSIMprofiles for different types of user devices.
 11. The one or morenon-transitory computer-readable media of claim 3, wherein a serviceparameter includes a geographical location of the user device, an RSPplatform availability requirement, an RSP platform response timerequirement for an eSIM profile request, an RSP platform reliabilityrequirement, or an RSP platform inventory requirement.
 12. The one ormore non-transitory computer-readable media of claim 1, wherein aservice feature of an RSP platform or a service parameter associatedwith the user device includes an ability of the eSIM profile distributedby the RSP platform to hold user device data, an ability of thecorresponding RSP platform to prioritize eSIM profile download to theuser device, or an ability to update a third-party manager of the eSIMprofile regarding an inventory status of eSIM profiles having the sametype as the eSIM profile.
 13. A user device, comprising: one or moreprocessors; and memory including a plurality of computer-executablecomponents that are executable by the one or more processors to performa plurality of actions, the plurality of actions comprising: receiving alist of preferred remote SIM provisioning (RSP) platforms that aredesignated by a mobile network operator (MNO) to distribute eSIMprofiles of a partner MNO of the MNO, the partner MNO providingtelecommunication services in a geographical area via a wireless carriernetwork; obtaining from a meta RSP interface (MRI) platform a list ofavailable RSP platforms that are able to distribute the eSIM profiles ofthe partner MNO in response to determining that the user device is inthe geographical area; identifying a most preferred RSP in the list ofavailable of RSP platforms using the list of preferred RSP platforms;and requesting a download of an eSIM profile from the most preferred RSPplatform to access the telecommunication services from the wirelesscarrier network of the partner MNO.
 14. The user device of claim 13,wherein the determining that the user device is in the geographical areaincludes determining that the user device has moved from an additionalgeographical area to the geographical area, the additional geographicalarea being serviced by an additional wireless carrier network of the MNOor an additional partner MNO of the MNO.
 15. The user device of claim13, wherein the plurality of actions further comprise storing the eSIMprofile from the most preferred platform in an eSIM of the user device.16. The user device of claim 13, wherein the plurality of actionsfurther comprise, in response to the most preferred RSP platform beingunable to provide the eSIM profile in a predetermined period of time:identifying a next most preferred RSP in the list of available of RSPplatforms using the list of preferred RSP platforms; and requesting thedownload of the eSIM profile from the next most preferred RSP platformto access the telecommunication services from the wireless carriernetwork of the partner MNO.
 17. A computer-implemented method,comprising: aggregating information on service features of multipleremote SIM provisioning (RSP) platforms at a meta RSP interface (MRI)platform; storing the information on the service features the multipleRSP platforms in a service feature data store of the MRI platform;receiving, at the MRI platform, a request for information on servicefeatures of individual RSP platforms in a list of RSP platforms from alocal profile assistant (LPA) application of a user device; anddistributing the information on the service features of the individualRSP platforms to the LPA application of the user device such that theLPA application selects an RSP platform from which to download an eSIMprofile based on the service features, the eSIM profile providing theuser device with access to telecommunication services of a mobilenetwork operator (MNO).
 18. The computer-implemented method of claim 17,wherein the receiving includes receiving the request from the LPAapplication following the user device relocating to a geographical areaserviced by a wireless carrier network of the MNO from an additionalgeographical area serviced by an additional wireless carrier network ofa different MNO.
 19. The computer-implemented method of claim 17,wherein the service features of an RSP platform include a geographicalarea serviced by the RSP platform, an availability of the RSP todistribute eSIM profiles, a representative response time of the RSPplatform to requests for the eSIM profiles, a reliability of the RSPplatform in distributing the eSIM profiles, or available inventoryquantities of specific eSIM profiles for different types of userdevices.
 20. The computer-implemented method of claim 19, wherein theservice features of the RSP platform further include an ability of theeSIM profile distributed by the RSP platform to hold user device data,an ability of the corresponding RSP platform to prioritize eSIM profiledownload to the user device, or an ability to update a third-partymanager of the eSIM profile regarding an inventory status of eSIMprofiles having the same type as the eSIM profile.